<%
=begin
apps: wavefront-prometheus-storage-adapter
platforms: kubernetes, tanzu-application-catalog
id: configure_connection
title: Connect to a Wavefront Proxy instance
category: get-started
weight: 20
highlight: 20
=end %>

This chart needs to be connected to a Wavefront Proxy instance. This can be done in three different ways:

* Deploying the Wavefront subchart using only the Wavefront Proxy component (default behavior): This is done by setting the *wavefront.enabled=true* and *wavefront.proxy.enabled=true* chart parameters. In this case, the *externalProxy.host* value should be left unset. Configure the Wavefront SaaS URL and token using the *wavefont.wavefront.url* and *wavefront.wavefront.token* parameters. Here is an example (remember to replace the WAVEFRONT-URL and WAVEFRONT-TOKEN placeholders with the correct URL and token):

    ```yaml
    externalProxy:
      host:
      port:
    wavefront:
      enabled: true
      collector:
        enabled: false
      rbac:
        create: false
      serviceAccount:
        create: false
      proxy:
        enabled: true
      wavefront:
        url: http://WAVEFRONT-URL
        token: WAVEFRONT-TOKEN
    ```

  > NOTE: Under this approach, it is recommended to disable the rest of the Wavefront sub-chart resources as they would not be used.

* Using an external Wavefront Proxy instance: This is done by setting the *externalProxy.host* and *externalProxy.port* values. In this case, set the *wavefront.enabled* value to *false*. Configure the Wavefront SaaS URL and token using the *wavefont.wavefront.url* and *wavefront.wavefront.token* parameters. Here is an example (remember to replace the WAVEFRONT-URL and WAVEFRONT-TOKEN placeholders with the correct URL and token):

    ```yaml
    externalProxy:
      host: example-proxy
      port: 2878
    wavefront:
      enabled: false
      wavefront:
        url: http://WAVEFRONT-URL
        token: WAVEFRONT-TOKEN
    ```
